home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
program
/
vbprnt20.zip
/
SRC
/
README
next >
Wrap
Text File
|
1996-05-31
|
2KB
|
48 lines
The DLLs were compiled using Borland C++ 4.5, and there are three flavors:
Visual Basic 3.0 uses the following files:
VBPRINT.C
VBAPI.LIB
VBPRNT16.DEF
VBPRNT16.RC
->Compiles to VBPRINT.DLL (Declares and Consts in VBPRINT.BAS)
Visual Basic 4.0 16-Bit uses the following files:
VBPRNT32.C
VBPRNT16.DEF
VBPRNT16.RC
->Compiles to VBPRNT16.DLL (Declares and Consts in VBPRNT32.BAS)
Visual Basic 4.0 32-bit uses the following files:
VBPRNT32.C
VBPRNT32.DEF
VBPRNT32.RC
->Compiles to VBPRNT32.DLL (Declares and Consts in VBPRNT32.BAS)
The VBDeviceCapabilities() function call is different in the VB3 version of
the DLL. While VB4.0/16-bit is fully compatible with it and your VB3 apps
will port flawlessly to VB4/16-bit, you will have to make some modifications
to your code if you want to port it to VB4/32-bit.
However, if you are writing in native VB4 and not coming from VB3, DO NOT USE
VBPRINT.DLL IF YOU DON'T HAVE TO! Use the VB4 versions instead so that your
16-bit and 32-bit VB programs will be fully compatible.
Why two whole .C files instead of one?
Because VB3 accesses strings entirely different than VB4 (VB4 uses OLECHARs
and VB3 uses HLSTRs) and all the string access functions are different.
Rather than spend a lot of time confusing myself with #ifdef statements and
redundant sections of code, I figured I'd save myself the headache and just
throw it into a seperate .C file. Most everyone is using VB4 nowadays
anyway, so you'll probably spend most of your time digging around in the
VBPRNT32.C file.
Robert Simpson
Programmer at Large
BC Software
Phx, AZ
simpson@primenet.com